release: 0.11.0#330
Open
stainless-app[bot] wants to merge 92 commits intomainfrom
Open
Conversation
91abc1a to
de14ac0
Compare
de14ac0 to
e88491a
Compare
e88491a to
3432a16
Compare
3432a16 to
d09931b
Compare
d09931b to
caf0668
Compare
caf0668 to
1bb322c
Compare
1bb322c to
e423419
Compare
e423419 to
8a63a77
Compare
8a63a77 to
9ccf90e
Compare
9ccf90e to
dc63a90
Compare
dc63a90 to
9dc2cc1
Compare
9dc2cc1 to
89702a7
Compare
89702a7 to
341713c
Compare
341713c to
4fd88a7
Compare
2861de8 to
bc750c9
Compare
bc750c9 to
471c0b9
Compare
471c0b9 to
08e41f5
Compare
08e41f5 to
f53228b
Compare
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Wed, 27 May 2026 22:27:04 GMT |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated Release PR
0.11.0 (2026-04-29)
Full Changelog: v0.10.2...v0.11.0
Features
Bug Fixes
Chores
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions
Greptile Summary
This automated release PR bumps the SDK from
0.10.2to0.11.0with three substantive changes: (1) a newAGENTEX_CUSTOM_HEADERSenv-var feature for injecting headers without code changes, (2) a bug fix making multipart file-array field names respect a configurablearray_format, and (3) an API update removingtask_idfrom all span endpoints. All changes are generated by Stainless and appear clean, with only two minor P2 findings.Confidence Score: 5/5
Safe to merge — all remaining findings are P2 style/robustness items with no impact on the primary code paths
No P0 or P1 issues found. The two P2 findings are: a silent header-drop edge case when default_headers is a tuple list alongside the env var (uncommon usage pattern), and a weakened test assertion that drops the field-name key check. Neither affects production behaviour for typical SDK consumers.
src/agentex/_client.py (header merging edge case) and tests/test_files.py (weakened assertion)
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Client.__init__] --> B{AGENTEX_CUSTOM_HEADERS set?} B -- No --> E[Pass default_headers as-is to super] B -- Yes --> C[Parse newline-delimited Key: Value pairs] C --> D{is_mapping_t default_headers?} D -- Yes --> F["Merge: {**parsed, **default_headers}"] D -- No --> G["Use parsed only (explicit headers dropped)"] F --> E G --> E H[extract_files call] --> I{array_format param} I -- brackets --> J["field[] for each item"] I -- indices --> K["field[0], field[1], ..."] I -- repeat/comma --> L["field (bare, repeated)"]Prompt To Fix All With AI
Reviews (89): Last reviewed commit: "release: 0.11.0" | Re-trigger Greptile